The Jupiter only updates it's time and position once per second. So between the PPS pulses, the 10 kHz is essentially free running from the receiver's internal crystal. It does not have the computation power to do more. More modern receivers with higher power CPUs can update their solution several times per second. I am not sure any commercial receiver will do much more than that. Military receivers are a different story, but you won't find one of those on eBay :-)

The 10 kHz output allows to make a simpler implementation of a GPSDO as James Miller describes on his web site, but it does not allow to shorten the time constant of the loop because the main correction component is still at 1 Hz, and the receiver has a little more jitter than more recent designs. So when mated to a high performance OCXO, the time constant should be long. To find out, plot the ADEV of the GPS and the ADEV of the Jupiter, and where they cross is where you want the loop bandwidth to be. There are lots of nice plots of GPS receivers and OCXOs on the Tom Van Baak web site www.leapsecond.com. That will give you an idea of what to look for. I do not believe Tom has plotted a Jupiter?

If you are interested in a simple frequency reference with modest acuracy, the Jupiter saves you a few counters. The James Miller design is the simplest, functional (and quite useful) GPSDO I have seen.

To check your Rb against the Jupiter, use a two channel digital storage scope, trigger it on the PPS and look for drift in the Rb, then adjust the Rb to minimize drift.

That will give you a quick indication of it's stability, but not one you can easily quantify.

Didier KO4BB